System and method for detecting and alerting risks of inputting incorrect account information in refill transactions

ABSTRACT

Apparatus and method are disclosed for detecting a risk in a refill transaction. The method may include receiving, from a user, a request for refilling an account, the request including account information associated with the account. The method may also include acquiring a contact information set corresponding to the user. The method may further include determining whether the contact information set includes the account information by searching in the contact information set for information matching the account information. In addition, the method may include providing a risk alert to the user if it is determined that the contact information set does not include the account information.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of Ser. No. 14/812,806 filed Jul. 29,2015, which is based upon and claims priority to Chinese Application No.201410377859.4, filed Aug. 1, 2014, both of which are incorporatedherein by reference in their entirities.

TECHNICAL FIELD

The present application relates to terminal devices, and moreparticularly, to apparatus and method for detecting and alerting risksin refill transactions.

BACKGROUND

Refilling service fee to a prepaid cell phone service is a commonpractice. A user can refill or prepay a certain amount of money forhis/her cell phone beforehand, and the service provider can deduct anactual service charge directly from the prepaid amount. In this way, theuser does not need to visit the service provider's store to pay a bill.

Similar refill activities have been used in more and more scenarios,such as refill of virtual currency/game currency, refill of online gametime, and refill of smart electricity cards over the Internet. Usually,each refill account has a unique account number, and the refillprocedure is to associate the refill amount with a corresponding accountnumber, thereby providing a prepaid credit for future debits.

The account number of the refill account is generally formed by aplurality of numbers, letters, etc. As a result, when the user inputsthe account number manually, it is easy to make mistakes. If the userdoes not check the input account number carefully, it may causerefilling of an incorrect account number, thereby resulting in financialloss.

SUMMARY

In one aspect, the present disclosure is directed to a method fordetecting a risk in a refill transaction. The method may includereceiving, from a user, a request for refilling an account, the requestincluding account information associated with the account. The methodmay also include acquiring a contact information set corresponding tothe user. The method may further include determining, by the processordevice, whether the contact information set includes the accountinformation by searching in the contact information set for informationmatching the account information. In addition, the method may includeproviding a risk alert to the user if it is determined that the contactinformation set does not include the account information.

In another aspect, the present disclosure is directed to an apparatus.The apparatus may include a memory device and a processor devicecommunicatively coupled to the memory device. The processor device maybe configured to receive, from a user, a request for refilling anaccount, the request including account information associated with theaccount. The processor device may also be configured to acquire acontact information set corresponding to the user. The processor devicemay further be configured to determine whether the contact informationset includes the account information by searching in the contactinformation set for information matching the account information. Inaddition, the processor device may be configured to provide a risk alertto the user if it is determined that the contact information set doesnot include the account information.

In a further aspect, the present disclosure is directed to anon-transitory, computer-readable medium storing instructions that, whenexecuted by a processor device, cause the processor device to perform amethod for detecting a risk in a refill transaction. The method mayinclude receiving, from a user, a request for refilling an account, therequest including account information associated with the account. Themethod may also include acquiring a contact information setcorresponding to the user. The method may further include determining,by the processor device, whether the contact information set includesthe account information by searching in the contact information set forinformation matching the account information. In addition, the methodmay include providing a risk alert to the user if it is determined thatthe contact information set does not include the account information.

Additional objects and advantages of the present disclosure will be setforth in part in the following detailed description, and in part will beobvious from the description, or may be learned by practice of thepresent disclosure. The objects and advantages of the present disclosurewill be realized and attained by means of the elements and combinationsparticularly pointed out in the appended claims.

It is to be understood that the foregoing general description and thefollowing detailed description are exemplary and explanatory only, andare not restrictive of the invention, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which constitute a part of thisspecification, illustrate several embodiments and, together with thedescription, serve to explain the disclosed principles.

FIG. 1 is a flow chart of an exemplary method for detecting refilltransaction risks, according to an embodiment of the presentapplication.

FIG. 2 is a flow chart of an exemplary method for detecting refilltransaction risks, according to another embodiment of the presentapplication.

FIGS. 3A-3D are schematic diagrams of exemplary interfaces, according toembodiments of the present application.

FIG. 4 is a flow chart of another exemplary method for detecting refilltransaction risks, according to an embodiment of the presentapplication.

FIG. 5 is a schematic diagram of another exemplary interface, accordingto an embodiment of the present application.

FIG. 6 is a block diagram of an exemplary electronic device, accordingto an embodiment of the present application.

FIG. 7 is a functional block diagram of an exemplary risk alertingrefill module, according to an exemplary embodiment of the presentapplication.

DETAILED DESCRIPTION

Reference will now be made in detail to exemplary embodiments of theinvention, examples of which are illustrated in the accompanyingdrawings. When appropriate, the same reference numbers are usedthroughout the drawings to refer to the same or like parts.

Embodiments of the present application may detect risks in refilltransactions and provide alerts to a user performing the refilloperation. For example, some embodiments may verify a refill accountnumber and determine the identity of the refill account number or arelationship between the user performing the refill action and therefill account number to prevent errors caused by an incorrect input andto avoid financial loss of the user.

FIG. 1 is a flow chart of an exemplary method 100 for detecting refilltransaction risks.

As shown in FIG. 1, method 100 includes several steps. One or more stepsmay be optional.

In Step 102, a request for refilling an account may be received from auser performing the refill operation. The request may carry accountinformation associated with the account, such as a refill accountnumber.

In this embodiment, the user can perform a refill operation using anyelectronic device that can be connected to the Internet. For example,mobile devices such as cell phones, tablet computers, notebookcomputers, desktop computers, smart TVs, or any other suitableelectronic devices. When performing the refill operation, the user maydesignate a specific refill account by inputting a refill accountnumber. For example, when refilling a prepaid cell phone account, therefill account number may be a cell phone number. In another example,when refilling a virtual currency account, the refill account number maybe a user name or a user account number of a corresponding virtualcurrency platform. In another example, when refilling an online gameplaytime, the refill account number may be a game account number.

In Step 104, a contact information set corresponding to the user may beacquired.

In this embodiment, by including multiple contact information sources,information in the contact information set may be used to cover a broadrange of contacts of the user. Several exemplary contact informationsources are described as follows. Other suitable sources may also beused.

For example, when the user performs a refill operation using a cellphone account, one contact information source may be an electronicaddress book stored locally in the cell phone. Therefore, the contactinformation set may include contact information corresponding to theuser obtained from the electronic address book. The user may also useother electronic devices such as a tablet computer to refill a cellphone account. In some embodiments, contact information created by theuser and stored in the electronic address book of the cell phone can beobtained using a synchronizing function to synchronize the electronicaddress book to other electronic device. For example, an electronicdevice, such as a table computer, may send an acquisition request to aserver storing the electronic address book and receive the contactinformation corresponding to the user returned by the server.

The contact information in the electronic address book may be created bythe user manually, and may be associated with the user's family,friends, or relatives. In other words, these contacts are likely knownby the user. When the refill account number input by the user matchesinformation of a certain contact in the electronic address book, thepossibility that the user makes mistakes in inputting the account numberis relatively low.

As another example, the contact information source may be a refillplatform corresponding to a refill webpage, such as “Alipay” or“Taobao.” The user may register an account in the refill platform, andmay use the account to log into the refill platform and then performspecific refill operations. In this case, the contact information setmay include contact information corresponding to the login account ofthe user in the refill platform.

Besides the electronic address book and the refill platform, many otherthird-party applications may also have their own contact informationsystems. Therefore, contact information in the third-party applicationscan also be obtained for verifying the refill account number input bythe user. However, it is noted that some third-party applications mayhave data security problems, especially for applications in refillplatform. Therefore, data from third-party applications may not bereliable and may cause security risks.

In Step 106, a determination may be made by, for example, a processordevice, to determine whether the contact information set includes theaccount information, e.g., the refill account number input by the user.The processor device may search in the contact information set forinformation matching the account information input by the user.

In some embodiments, multiple contact information sources can becombined. For example, electronic address book may be combined withrefill platform. In this case, the contact information set may includefirst contact information corresponding to the user obtained from theelectronic address book and second contact information corresponding tothe login account of the user used in the refill platform. In this case,the searching for the refill account number in the contact informationset can be divided into two stages.

In the first stage, the processor device may determine whether the firstcontact information (contact information corresponding to the userobtained from the electronic address book) includes the accountinformation input by the user. For example, the processor device maysearch in the first contact information for information matching theaccount information inputted by the user. If the first contactinformation does not include the account information, the process mayenter the second stage, in which the processor device may determinewhether the second contact information (contact informationcorresponding to the login account of the user used in the refillplatform) includes the account information input by the user. Forexample, the processor device may search in the second contactinformation for information matching the account information inputted bythe user. In some embodiments, the second contact information may beacquired before the first stage. In other embodiments, the secondcontact information may be acquired upon the completion of the firststage and as supplemental information. Dividing the searching processinto two stages may reduce the data quantity of the contact informationduring each of the searching stages.

The contact information sources, e.g., electronic address book, refillplatform, and/or third-party applications may be used to obtain thecontact information, and multiple data acquisition modes may beemployed. For example, contact information corresponding to the user maybe stored locally and/or on a server. When the contact information isstored locally, the processor device may retrieve the contractinformation by accessing the local data storage or memory. When thecontact information is stored on a server, the processor device may sendan acquisition request to the server and receive the contact informationreturned by the server.

In Step 108, a risk alert may be provided to the user, e.g., through aninterface, if the contact information set does not include the accountinformation input by the user. For example, if the searching operationdoes not yield any matching contact in the contact information set, itis likely that the account information input by the user containserrors, such as one or more wrong numbers or misspells due to fatfingers.

By matching a refill account number input by the user with contactinformation in the contact information set, the processor device maycheck if the refill account number has any relationship with the user.If the refill account number belongs to a stranger that has no apparentrelationships with the user, such refill account number may bemistakenly input by the user. In this case, the processor device mayissue a risk alert to notify the user to double check if any inputtingmistake occurs, thereby avoiding financial loss to the user.

FIG. 2 is a flow chart of an exemplary method 200 for detecting refilltransaction risks. Method 200 start from step 202, in which a refillprocess is triggered by a user, referred to hereafter as User A. Forexample, User A may use a certain refill application M on a cell phoneto refill a cell phone account of another user, referred to hereafter asUser B. Once a cell phone service fee refill function of the refillapplication M is triggered by User A, the cell phone may display aninterface 310 shown in FIG. 3A, to prompt User A to input a phone numberof User B in an input block 312. User A may also choose or input aspecific refilling amount, such as $50.00 shown in block 314.

In Step 204, a cell phone number input by User A may be acquired. Forexample, referring to FIG. 3B, the cell phone number “202 456 7890”input into block 312 may be acquired by the processor device.

In Step 206, the processor device may access the electronic address bookcorresponding to User A. The electronic address book may be stored inthe cell phone used by User A to perform the refill operation, e.g., ina memory card of the cell phone, or in a Subscriber Identity Module(SIM) card. Alternatively or additionally, the electronic address bookmay be stored on a server. In this case, User A's account information(e.g., User A's ID number, cell phone number, etc.) may be used to loginto the server, for acquiring and/or synchronizing the content of theelectronic address book from the server. The acquisition and/orsynchronization may be performed periodically or in real time.

In Step 208, the content of the electronic address book, e.g., thecontact information corresponding to User A, is used to search forinformation matching the cell phone number input by User A. If contactinformation matching the cell phone number input by User A is found, theprocess proceeds to Step 210; otherwise, the process proceeds to Step212.

If contact information matching the cell phone number input by User A isfound in the electronic address book, the interface shown in FIG. 3B maybe displayed. As shown in FIG. 3B, an icon such as “√” can be used toindicate that the cell phone number input by User A is found in theelectronic address book. In addition, the corresponding contactinformation, e.g., the name of the contact—John Smith, may be shown toallow User A to confirm whether the input cell phone number belongs toUser B.

In Step 210, the refill transaction is complete. For example, User A maypress button 316 shown in FIG. 3B to finish the refill transaction.

In Step 212, the processor device may access the electronic address bookcorresponding to User A saved on the refill platform. For example, theprocessor device may retrieve contact information of User A in refillapplication M when application M is associated with the refill platform.In some embodiments, the locally stored electronic address book may bedifferent from the electronic address book retrieve in refillapplication M. Thus, the contact information respectively retrieved inStep 206 and Step 212 may be different but may also contain overlappingcontent.

In Step 214, the contact information retrieved in refill application Mmay be used to search for information matching the cell phone numberinput by User A. If contact information matching the cell phone numberinput by User A is found, the process proceeds to Step 210; otherwise,the process proceeds to Step 216.

In some embodiments, when the contact information matching the cellphone number input by User A is found in the electronic address bookretrieved in refill application M, the interface shown in FIG. 3B may bedisplayed, indicating that the input cell phone number is likelycorrect.

In Step 216, the processor may issue a risk alert. In some embodiments,the interface shown in FIG. 3C may be displayed, in which alertindicators such as “×”, “Unknown”, or “Not Found” may be used toindicate that the cell phone number input by User A is not found, andUser A may risk refilling to a incorrect account. The risk alert may beused to notify User A to double-check the input phone number. In anotherexample, interface shown in FIG. 3D may be displayed. In FIG. 3D, analert message may be displayed. Alternatively or additionally, an alerticon such as “Θ” may be displayed to notify User A that the inputtelephone number may be incorrect.

In the above description, cell phone number is used as an example todisclose embodiments of the present application. The disclosed methodand system are also applicable to other types of account information,such as cable services, utility services, Internet services, onlinegaming, etc.

In some embodiments, since User A likely knows the cell phone number ofUser B, the input telephone number, even containing errors, may only beoff a few digits. That is, the input number may be partially correct andpartially incorrect. In view of this, the present application furtherprovides another exemplary risk alerting method 400 shown in FIG. 4.

Method 400 may be carried out following the NO branch of Step 214 inFIG. 2. In Step 402, after the two stage searching operations in FIG. 2,it may be determined that the contact information set does not includematching contact information because no contact matching the refillaccount number input by User A can be found. For example, assume thatthe refill account number input by User A is a telephone number “202 4566890,” as shown in FIG. 3C.

In Step 404, a searching operation is performed in the contactinformation set corresponding to User A by, for example, using therefill account number (e.g., the cell phone number 202 456 6890) as akey word to search for a cell phone number partially matching “202 4566890.”

In Step 406, based on searching results, if one or more partiallymatched telephone numbers are found (e.g., at least a predeterminednumber of digits match the input telephone number), a similarity of eachmatching result with respect to the input telephone number isdetermined. For example, the similarity may be quantified by the numberof digits that match the input telephone number. If a certain matchingresult has a similarity higher than or equal to a preset similaritythreshold (Step 406), the process may proceed to Step 408; otherwise,the process may make further determination, until all partially matchedresults are traversed.

In Step 408, the partially matched result may be displayed to the userthrough an interface, such as interface 320 shown in FIG. 5.

In some embodiments, the preset similarity threshold may be set by adeveloper beforehand, or may be edited and adjusted by the user duringthe usage stage. As shown in FIG. 5, interface 320 may also display analert message 322, suggesting that there may be an error in the inputtelephone number and the suggested correct number.

In some embodiments, the processor device may compare the inputtelephone number and the partially matched result (e.g., the suggestedcorrect number) and determine a matched portion and a non-matchedportion. For example, in the example shown in FIG. 5, the non-matchedportion is the seventh digit, and matched portion includes all otherdigits. The matched portion and the non-matched portion may also bedisplayed in different manners. For example, while the matched portionmay be displayed in a regular fashion, the non-matched portion,indicating the difference between the input telephone number and thesuggested correct number, may be displayed in an emphasized manner. Forexample, in FIG. 5, a block is added to the seventh digit in both theinput telephone number and the suggested correct number. A personskilled in the art can understand that the matched portion and thenon-matched portion may also be displayed in other ways, for example, byusing different colors or by highlighting, which are all applicable tothe technical solutions of the present application.

FIG. 6 is a block diagram of an exemplary electronic device 600 forimplementing the above-disclosed technical solutions. Referring to FIG.6, electronic device 600 may include a processor device 610, a bus 620,a network interface 630, a memory device 640, and a non-volatile storage650. Processor device 610 may execute instructions of a computersoftware program stored in non-volatile storage 650 and loaded in memorydevice 640 to perform various functions of the risk alert methodsdisclosed above. The software program may be functionally recognized asa risk alerting refill module 645 stored in non-volatile storage 650 or645′ when loaded into memory device 640. In some embodiments, riskalerting refill module 645 may be part of an application system thatprovides services to users. Other forms of implementations of theabove-disclosed functions such as using logic devices or combinedsoftware and hardware, are also contemplated by this disclosure.

FIG. 7 is a functional block diagram of an exemplary implementation ofrisk alerting refill module 645. Referring to FIG. 7, risk alertingrefill module 645 may include a receiving unit 710, a searching unit720, an acquiring unit 730, a display unit 740, a locating unit 750, acomparing unit 760, and an alerting unit 770.

Receiving unit 710 may be configured to receive, from a user, a requestfor refilling an account. The request may include account informationassociated with the account.

Acquiring unit 730 may be configured to acquire a contact informationset corresponding to the current user.

Searching unit 720 may be configured to search in the contactinformation set for information matching the account information.

Alerting unit 770 may be configured to provide a risk alert to the user.

Displaying unit 740 may be configured to display an interface, a riskalert, partially matched result, and other information to the user.

Locating unit 750 may be configured to locate and retrieve contactinformation.

Comparing unit 760 may be configured to compare a partially matchedresult with account information input by the user.

Processor device 610 may include one or more central processing units(CPUs). Electronic device 600 may include an input/output interface (I/Ointerface).

Memory device 640 may include a volatile memory, a Random Access Memory(RAM), and/or a non-volatile memory (NVM) such as a Read Only Memory(ROM) or a flash memory.

The specification has described apparatuses and methods for detectingrisks in refill transactions. The illustrated steps are set out toexplain the exemplary embodiments shown, and it should be anticipatedthat ongoing technological development will change the manner in whichparticular functions are performed. Thus, these examples are presentedherein for purposes of illustration, and not limitation. For example,steps or processes disclosed herein are not limited to being perforatedin the order described, but may be performed in any order, and somesteps may be omitted, consistent with disclosed embodiments. Further,the boundaries of the functional building blocks have been arbitrarilydefined herein for the convenience of the description. Alternativeboundaries can be defined so long as the specified functions andrelationships thereof are appropriately performed. Alternatives(including equivalents, extensions, variations, deviations, etc., ofthose described herein) will be apparent to persons skilled in therelevant art(s) based on the teachings contained herein. Suchalternatives fall within the scope and spirit of the disclosedembodiments.

While examples and features of disclosed principles are describedherein, modifications, adaptations, and other implementations arepossible without departing from the spirit and scope of the disclosedembodiments. Also, the words “comprising,” “having,” “containing,” and“including,” and other similar forms are intended to be equivalent inmeaning and be open ended in that an item or items following any one ofthese words is not meant to be an exhaustive listing of such item oritems, or meant to be limited to only the listed item or items. It mustalso be noted that as used herein and in the appended claims, thesingular forms “a,” “an,” and “the” include plural references unless thecontext clearly dictates otherwise.

Furthermore, one or more computer-readable storage media may be utilizedin implementing embodiments consistent with the present disclosure. Acomputer-readable storage medium refers to any type of physical memoryon which information or data readable by a processor may be stored.Thus, a computer-readable storage medium may store instructions forexecution by one or more processors, including instructions for causingthe processor(s) to perform steps or stages consistent with theembodiments described herein. The term “computer-readable medium” shouldbe understood to include tangible items and exclude carrier waves andtransient signals, i.e., be non-transitory. Examples include RAM, ROM,volatile memory, nonvolatile memory, hard drives, CD ROMs, DVDs, flashdrives, disks, and any other known physical storage media.

It is intended that the disclosure and examples be considered asexemplary only, with a true scope and spirit of disclosed embodimentsbeing indicated by the following claims.

What is claimed is:
 1. A method, implemented by a processor device, fordetecting a risk in a refill transaction, comprising: receiving, from auser, a request for refilling an account, the request including accountinformation associated with the account; acquiring a contact informationset corresponding to the user; determining, by the processor device,whether the contact information set includes the account information anddisplaying, responsive to the determination that the contact informationset does not include the account information and the contact informationset includes information partially matching the account information, amatched portion and a non-matched portion of the partially matchedcontact information in different manners, wherein the non-matchedportion corresponds to a portion of the partially matched contactinformation that is different from a corresponding portion of theaccount information and wherein the matched portion corresponds to aportion of the partially matched contact information that is the same asa corresponding portion of the account information.
 2. The method ofclaim 1, wherein the contact information set includes contactinformation corresponding to the user obtained from an electronicaddress book.
 3. The method of claim 1, wherein the contact informationset includes contact information corresponding to a login account of theuser used in a refill platform.
 4. The method of claim 1, wherein thecontact information set includes: first contact informationcorresponding to the user obtained from an electronic address book; andsecond contact information corresponding to a login account of the userused in a refill platform; and wherein the method comprises: determiningwhether the first contact information includes the account informationby searching in the first contact information for information matchingthe account information; and determining, responsive to a determinationthat the first contact information does not include the accountinformation, whether the second contact information includes the accountinformation by searching in the second contact information forinformation matching the account information.
 5. The method of claim 1,wherein the contact information set includes contact informationcorresponding to the user and wherein the method includes: retrievingthe contact information corresponding to the user stored locally.
 6. Themethod of claim 1, wherein the contact information set includes contactinformation corresponding to the user and the method includes: sendingan acquisition request to a server; and receiving the contactinformation corresponding to the user returned by the server.
 7. Anapparatus, comprising: a memory device configured to store a set ofinstructions; and a processor device communicatively coupled to thememory device, wherein the processor device is configured to execute theset of instructions to cause the apparatus to: receive, from a user, arequest for refilling an account, the request including accountinformation associated with the account; acquire a contact informationset corresponding to the user; determine whether the contact informationset includes the account information; and display, in response to thedetermination that the contact information set does not include theaccount information and the contact information set includes informationpartially matching the account information, a matched portion and anon-matched portion of the partially matched contact information indifferent manners, wherein the non-matched portion corresponds to aportion of the partially matched contact information that is differentfrom a corresponding portion of the account information and wherein thematched portion corresponds to a portion of the partially matchedcontact information that is the same as a corresponding portion of theaccount information.
 8. The apparatus of claim 7, wherein the contactinformation set includes contact information corresponding to the userobtained from an electronic address book.
 9. The apparatus of claim 7,wherein the contact information set includes contact informationcorresponding to a login account of the user used in a refill platform.10. The apparatus of claim 7, wherein the contact information setincludes: first contact information corresponding to the user obtainedfrom an electronic address book; and second contact informationcorresponding to a login account of the user used in a refill platform;and wherein the processor device is configured to: determine whether thefirst contact information includes the account information by searchingin the first contact information for information matching the accountinformation; and if the first contact information does not include theaccount information, determine whether the second contact informationincludes the account information by searching in the second contactinformation for info! nation matching the account information.
 11. Theapparatus of claim 7, wherein the contact information set includescontact information corresponding to the user and wherein the processordevice is further configured to cause the apparatus to: retrieve thecontact information corresponding to the user stored locally.
 12. Theapparatus of claim 7, wherein the contact information set includescontact information corresponding to the user and wherein the processordevice is further configured to cause the apparatus to: send anacquisition request to a server; and receive the contact informationcorresponding to the user returned by the server.
 13. A non-transitory,computer-readable medium storing a set of instructions that isexecutable by at least one processor of an apparatus to cause theapparatus to perform a method for detecting a risk in a refilltransaction, the method comprising: receiving, from a user, a requestfor refilling an account, the request including account informationassociated with the account; acquiring a contact information setcorresponding to the user; determining, by the processor device, whetherthe contact information set includes the account information anddisplaying, responsive to the determination that the contact informationset does not include the account information, a matched portion and anon-matched portion of the partially matched contact information indifferent manners, wherein the non-matched portion corresponds to aportion of the partially matched contact information that is differentfrom a corresponding portion of the account information and wherein thematched portion corresponds to a portion of the partially matchedcontact information that is the same as a corresponding portion of theaccount information.
 14. The computer-readable medium of claim 13,wherein the contact information set includes at least one of: contactinformation corresponding to the user obtained from an electronicaddress book; or contact information corresponding to a login account ofthe user used in a refill platform.
 15. The computer-readable medium ofclaim 13, wherein the contact information set includes: first contactinformation corresponding to the user obtained from an electronicaddress book; and second contact information corresponding to a loginaccount of the user used in a refill platform; and wherein the set ofinstructions that is executable by the at least one processor of theapparatus to cause the apparatus to further perform: determining whetherthe first contact information includes the account information bysearching in the first contact information for information matching theaccount information; and if the first contact information does notinclude the account information, determining whether the second contactinformation includes the account information by searching in the secondcontact information for information matching the account information.